home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
3D Images
/
3D Images.iso
/
programs
/
amiga
/
smovie
/
smovie.tips
< prev
next >
Wrap
Text File
|
1995-01-12
|
5KB
|
122 lines
|spc 2; text spacing
|spd 2; scroll speed
|dep 2; this gives 4 colours but doesn't change size
|plt 0,7,3,5; background
|plt 1,15,15,15;white
|plt 2,0,15,0; green
|plt 3,15,15,0; yellow
|tab 4; each tab will advance to a column which is a multiple of four
|onc
|col 1,0
Tips part 1 - for single drive users
====================================
|ofc
Oh you poor thing! Go and buy yourself another drive.
Seriously though, disk swaps aren't much fun, so if you are
going to use sMOVIE much it's worth doing one of two things.
If you're happy with the CLI environment, you can put your
fonts on the same disk as sMOVIE and use the Assign command to
tell AmigaDos where to look for its fonts. Alternatively you
can create a stripped down Workbench disk with room for sMOVIE,
loadsa fonts, and all your projects.
Take a COPY of your workbench and delete the following:-
Everything in the Utilities directory.
Everything in the Prefs directory.
The Expansion, Prefs and Utilities directories.
Ed and Edit from the c directory unless you use them.
If you still use WB1.2 (cheapskate!) delete all the printers
and keymaps from the devs directory except those you use.
You could delete a lot of other stuff - but that's enough
to begin with. Be careful not to remove things that you think
you never use, but which might be accessed by the system. e.g.
the startup-sequence uses 'If' from the c: directory.
Now you've got lots of room in your fonts directory you
can go looking for some fonts.
|col 2,0
|onc
Tips part 2 - where to get some free fonts
==========================================
|ofc
1. WB 1.3 Extras disk has some extra fonts (bit obvious).
2. If, like me, you had a 'The Very First' demo bundled with
your Amiga, and you haven't already tossed it in the bin,
then you can copy some decent fonts from it. It had to have
some use!
3. Have a look through your other disks (even games sometimes!)
and see if there are any new fonts on them.
4. There are some P.D. disks which contain heaps of fonts.
|col 3,0
|onc
Tips part 3 - watch that memory (for techies)
=============================================
|ofc
Coo look! I can have a 704 * 261 size 16 colour screen and
ten different 46 pixel high fonts... Well you could, but then
again you might just run out of memory.
sMOVIE allocates a bitmap which caters for the maximum width
height and depth you specify - even if they don't occur at the
same time. Don't call for a sixteen colour screen if you only
need four at any one time - just reuse the four - this should be
obvious.
After using sMOVIE for the first time on a project, you may
find you have less free memory left than before.
I HATE programs which do this. This is due to the strange way
the system software handles fonts; once a font has been loaded
from disk, the system seems unwilling to unload it. You will
find that on subsequent uses of sMOVIE no extra memory is
consumed. The 'Notepad' program supplied by Commodore is
identical in this respect. I do not know if the memory can be
reclaimed by the system if it begins to run short, but I suspect
not. If anybody has a fix to this problem (if it is a problem)
perhaps they'll contact me.
|col 1,0
|onc
Tips part 4 - general
=====================
|ofc
1. When you're writing a fairly complex file for sMOVIE, call
it from the CLI while you're developing it. This gives you
a lot more information about syntax errors in your commands
then you will get from the WorkBench.
2. Edit the file 'sMOVIE.config' and place it in the ROOT
directory. This controls sMOVIE's default colours, font
and so on. You may prefer to put this file in your s:
directory, but remember that a config file in the root
directory will take precedence.
3. Experiment with sMOVIE's SIZ and SSZ commands. You will
find that attempting to move screens sideways beyond certain
limits or creating very tiny screens will cause the display
to do strange and unexpected things!
|col 2,0
|onc
Tips part 5 - quirks
====================
|ofc
1. From the workbench you can start sMOVIE on one project, and
then before its got going, start it again on another (or the
same) project. This produces interesting, but weird results
try it and see! You may need to use Left-Amiga M,N,B at the
end to get your WB screen back.
2. PopCLI and other screen-saving programs do work O.K. with
sMOVIE, but if they blank the screen while you're trying to
read it, this can be a pain. They will sometimes cause the
Intuition cursor to reappear when you don't want it.
3. There is no number 3 (Yet!)